Data transmission method, data transmitting end, data receiving end, data transmission system and computer readable storage medium

ABSTRACT

The present disclosure provides a data transmission method, related devices and system. The method includes: an upper layer transmits a data packet to a corresponding Service Data Adaptation Protocol (SDAP) entity, according to at least one of a network slice identifier, an SDAP identifier, a flow identifier or a session identifier; the SDAP entity adds the flow identifier to the data packet, and transmits the data packet with the flow identifier to a Packet Data Convergence Protocol (PDCP) entity corresponding to a Data Radio Bearer (DRB), according to a corresponding relationship between the SDAP entity and the DRB.

CROSS-REFERENCE TO RELATED APPLICATION

This patent application is a 35 USC § 371 U.S. national stage ofInternational Application No. PCT/CN2018/089979 filed on Jun. 5, 2018,which claims a priority to Chinese Patent Application No. 201710431213.3filed with the Chinese Patent Office on Jun. 8, 2017, which isincorporated by reference in its entirely.

TECHNICAL FIELD

The present disclosure relates to communication technologies, and moreparticularly, to a data transmission method, related devices and system.

BACKGROUND

It is well known that the 5G system has introduced a network-sideindication mechanism for Quality-of-Service (QoS). Therefore, during theprocess of transmitting uplink and downlink data, it is necessary to addQoS indication information (such as flow ID) of an Internet Protocol(IP) flow of a terminal, and this protocol layer is located on a PacketData Convergence Protocol (PDCP) layer.

However, in 5G QoS control, different data may correspond to differentnetwork slice (Slice). One network slice may include multiple ProtocolData Unit (PDU) sessions. One PDU session may include multiple flows.Therefore, how to implement the interaction among an upper layer, aService Data Adaptation Protocol (SDAP) entity and a PDCP entity becomesan urgent problem to be solved.

SUMMARY

In a first aspect, an embodiment of the present disclosure provides adata transmission method, applied to a data transmitting end, including:

transmitting, by an upper layer, a data packet to a correspondingService Data Adaptation Protocol (SDAP) entity, according to at leastone of: a network slice identifier, an SDAP identifier, a flowidentifier, or a session identifier;

adding, by the SDAP entity, the flow identifier to the data packet, and,transmitting the data packet with the flow identifier to a Packet DataConvergence Protocol (PDCP) entity corresponding to a Data Radio Bearer(DRB), according to a corresponding relationship between the SDAP entityand the DRB.

In a second aspect, an embodiment of the present disclosure alsoprovides a data transmission method, applied to a data receiving end,including:

receiving, by a PDCP entity, a data packet from a data transmitting end,transmitting the data packet to a corresponding SDAP entity, accordingto a flow identifier carried by the data packet; and,

forwarding, by the SDAP entity, the data packet to an applicationprotocol layer, or forwarding the data packet to a corresponding networkslice, flow and Protocol Data Unit (PDU) session.

In a third aspect, an embodiment of the present disclosure also providesa data transmitting end, including:

a first transmitting module, configured to enable an upper layer totransmit a data packet to a corresponding SDAP entity, according to atleast one of a network slice identifier, an SDAP identifier, a flowidentifier, or a session identifier,

a second transmitting module, configured to enable the SDAP entity toadd the flow ID to the data packet, and transmit the data packet withthe flow ID to a PDCP entity corresponding to a DRB, according to acorresponding relationship between the SDAP entity and the DRB.

In a fourth aspect, an embodiment of the present disclosure alsoprovides a data receiving end, including:

a receiving module, configured to enable a PDCP entity to receive a datapacket from a data transmitting end, transmit the data packet to acorresponding SDAP entity, according to a flow identifier carried by thedata packet; and,

a forwarding module, configured to enable the SDAP entity to forward thedata packet to an application protocol layer, or, forward the datapacket to a corresponding network slice, flow and PDU session.

In a fifth aspect, an embodiment of the present disclosure also providesa data transmitting end, including a processor, a memory, a networkinterface and a user interface, in which the processor, the memory, thenetwork interface and the user interface are coupled through a bussystem, the processor is configured to read a program from the memory,and perform steps of the data transmission method at the datatransmitting end, which is provided by embodiments of the presentdisclosure.

In a sixth aspect, an embodiment of the present disclosure also providesa data receiving end, including: a processor, a memory, a networkinterface and a user interface, in which the processor, the memory, thenetwork interface and the user interface are coupled through a bussystem, the processor is configured to read a program from the memory,and perform steps of the data transmission method at the data receivingend, which is provided by embodiments of the present disclosure.

In a seventh aspect, an embodiment of the present disclosure alsoprovides a data transmission system, including a data transmitting endand a data receiving end, which are provided by embodiments of thepresent disclosure.

In an eighth aspect, an embodiment of the present disclosure alsoprovides a computer readable storage medium, which stores a datatransmission program. When the data transmission program is executed bya processor, the processor is caused to perform steps of datatransmission method at the data transmitting end, which is provided byembodiments of the present disclosure.

In a ninth aspect, an embodiment of the present disclosure also providesa computer readable storage medium, which stores a data transmissionprogram. When the data transmission program is executed by a processor,the processor is caused to perform steps of data transmission method atthe data receiving end, which is provided by embodiments of the presentdisclosure.

BRIEF DESCRIPTION OF THE DRAWINGS

To describe the technical solutions in the embodiments of the presentdisclosure more clear, brief descriptions of attached figures needing tobe used during illustration of embodiments in the present disclosurewill be provided in the following. It is obvious that, attached figuresin the following descriptions are only some embodiments of the presentdisclosure. For persons having ordinary skill in the art, other attachedfigures may also be obtained according to these attached figures,without paying creative work.

FIG. 1 is a schematic diagram illustrating structure of a datatransmission system applied by an embodiment of the present disclosure;

FIG. 2 is a flowchart illustrating a data transmission method, inaccordance with an embodiment of the present disclosure;

FIG. 3 is a flowchart illustrating another data processing method, inaccordance with an embodiment of the present disclosure;

FIG. 4 is a schematic diagram illustrating a flow transmission, inaccordance with an embodiment of the present disclosure;

FIG. 5 is a schematic diagram illustrating another flow transmission, inaccordance with an embodiment of the present disclosure;

FIG. 6 is a schematic diagram illustrating another flow transmission, inaccordance with an embodiment of the present disclosure;

FIG. 7 is a schematic diagram illustrating another flow transmission, inaccordance with an embodiment of the present disclosure;

FIG. 8 is a schematic diagram illustrating another flow transmission, inaccordance with an embodiment of the present disclosure;

FIG. 9 is a flowchart illustrating another data transmission method, inaccordance with an embodiment of the present disclosure;

FIG. 10 is a flowchart illustrating another data transmission method, inaccordance with an embodiment of the present disclosure;

FIG. 11 is a flowchart illustrating a data processing method, inaccordance with an embodiment of the present disclosure;

FIG. 12 is a flowchart illustrating another data processing method, inaccordance with an embodiment of the present disclosure;

FIG. 13 is a flowchart illustrating another data processing method, inaccordance with an embodiment of the present disclosure;

FIG. 14 is a schematic diagram illustrating structure of a datatransmitting end, in accordance with an embodiment of the presentdisclosure;

FIG. 15 is a schematic diagram illustrating structure of another datatransmitting end, in accordance with an embodiment of the presentdisclosure;

FIG. 16 is a schematic diagram illustrating structure of another datatransmitting end, in accordance with an embodiment of the presentdisclosure;

FIG. 17 is a schematic diagram illustrating structure of another datatransmitting end, in accordance with an embodiment of the presentdisclosure;

FIG. 18 is a schematic diagram illustrating structure of a datareceiving end, in accordance with an embodiment of the presentdisclosure;

FIG. 19 is a schematic diagram illustrating structure of another datareceiving end, in accordance with an embodiment of the presentdisclosure;

FIG. 20 is a schematic diagram illustrating structure of a dataprocessing device, in accordance with an embodiment of the presentdisclosure;

FIG. 21 is a schematic diagram illustrating structure of another dataprocessing device, in accordance with an embodiment of the presentdisclosure;

FIG. 22 is a schematic diagram illustrating structure of another dataprocessing device, in accordance with an embodiment of the presentdisclosure;

FIG. 23 is a schematic diagram illustrating structure of another dataprocessing device, in accordance with an embodiment of the presentdisclosure;

FIG. 24 is a schematic diagram illustrating structure of another datatransmitting end, in accordance with an embodiment of the presentdisclosure;

FIG. 25 is a schematic diagram illustrating structure of another datareceiving end, in accordance with an embodiment of the presentdisclosure; and

FIG. 26 is a schematic diagram illustrating structure of still anotherdata processing device, in accordance with an embodiment of the presentdisclosure.

DETAILED DESCRIPTION

To describe the technical solutions in the embodiments of the presentdisclosure more clear, brief descriptions of attached figures needing tobe used during illustration of embodiments in the present disclosurewill be provided in the following. It is obvious that, attached figuresin the following descriptions are only some embodiments of the presentdisclosure. For persons having ordinary skill in the art, other attachedfigures may also be obtained according to these attached figures,without paying creative work.

With reference to FIG. 1, FIG. 1 is a schematic diagram illustratingstructure of a data transmission system, which is applicable by anembodiment of the present disclosure. As shown in FIG. 1, the datatransmission system includes a data transmitting end 11 and a datareceiving end 12. The data transmitting end 11 may be a user terminal,which may be also referred to as a User Equipment (UE), which may be aterminal device, e.g., a mobile phone, a Tablet Personal Computer, aLaptop Computer, a personal digital assistant (PDA), a Mobile InternetDevice (MID), or a Wearable Device. The data transmitting end 11 may bea network device, e.g., a Transmission Reception Point (TRP), or a basestation, in which the base station may be a macro station, e.g., a LongTerm Evolution (LTE) evolved Node B (eNB), 5G New Radio (NR) Node B(NB), and so on. The data transmitting end 11 may also be an AccessPoint (AP). It should be noted that, in the embodiments of the presentdisclosure, specific type of the data transmitting end 11 is notlimited. In the attached figure, an example is given, in which the datatransmitting end is a user terminal. The data receiving end 12 may be aUE, e.g., a terminal device, such as, a mobile phone, a tablet, alaptop, a PDA, a MID, or a Wearable Device. The data receiving end 12may also be a network device, e.g., TRP, or a base station, in which thebase station may be a macro station, such as, LTE eNB, 5G NR NB, and soon. The data receiving end 12 may be the AP. It should be noted that, inthe embodiments of the present disclosure, specific type of datareceiving end 12 is not limited. In the attached figure, an example isprovided, in which the data receiving end 12 is a network device.

It should be noted that, in the embodiments of the present disclosure,specific types of data transmitting end 11 and data receiving end 12 arenot limited. Specific functions of data transmitting end 11 and datareceiving end 12 will be described in detailed, accompanying withmultiple embodiments in the following.

With reference to FIG. 2, FIG. 2 is a flowchart illustrating a datatransmission method, in accordance with an embodiment of the presentdisclosure. The method is applied to a data transmitting end. As shownin FIG. 2, the method includes the following step.

In step 201, an upper layer transmits a data packet to a correspondingSDAP entity, according to at least one of a network slice identifier(ID), an SDAP ID, a flow ID and a session ID.

The foregoing network slice ID may be configured to identify a networkslice, to which foregoing data packet belongs. And, the network slicemay include multiple session units (such as, PDU session). A PDU sessionmay include multiple flows. A flow ID may be configured to identify aflow, to which foregoing data packet belongs. Foregoing session ID maybe configured to identify a PDU session corresponding to the flow, towhich foregoing data packet belongs. In the step, a corresponding SDAPID is determined, according to the network slice ID of the data packet,the flow ID or session ID. And, the data is transmitted to thecorresponding SDAP entity.

In step 202, the SDAP entity adds the flow ID to the data packet, andtransmits the data packet with the flow ID to a PDCP entitycorresponding to a Data Radio Bearer (DRB), according to a correspondingrelationship between SDAP entity and DRB.

The foregoing corresponding relationship between SDAP entity and DRB maybe preset. After the flow ID is added to foregoing data packet, the IDof the corresponding flow is added to the data packet. However, the flowID of the data packet may be added, according to network presetconfiguration. The PDCP entity corresponding to the DRB may be preset,e.g., one DRB corresponds to one PDCP entity, or multiple DRBscorrespond to the same PDCP entity, and so on.

In addition, in the embodiment of the present disclosure, foregoing datapacket may be a Transmission Control Protocol (TCP)/IP data packet.

In the embodiment, the upper layer transmits the data packet to thecorresponding SDAP entity, according to at least one of the networkslice ID, the SDAP ID, the flow ID, the session ID. The SDAP entity addsthe flow ID to the data packet, and transmits the data packet with theflow ID to the PDCP entity corresponding to the DRB, according to thecorresponding relationship between SDAP entity and DRB. Subsequently,the interaction among the upper layer, SDAP entity and PDCP entity isimplemented.

With reference to FIG. 3, FIG. 3 is a flowchart illustrating anotherdata transmission method, in accordance with an embodiment of thepresent disclosure. The method is applied to a data transmitting end. Asshown in FIG. 3, the method includes the following steps.

In step 301, an SDAP entity is established in advance according toconfiguration information which is configured by a network orpre-defined.

The configuration information includes at least one of: a network sliceID, a DRB ID, a flow ID, a session ID, association relationshipindication information.

Foregoing association relationship indication information may indicate acorresponding relationship between above SDAP entity and other entity.Subsequently, in step 301, after receiving foregoing configurationinformation, the corresponding SDAP entity may be established.

In step 302, corresponding relationship information of the SDAP entityis indicated to the upper layer through the SDAP entity.

The corresponding relationship information includes at least one of: anetwork slice ID, a DRB ID, a flow ID, a session ID and an SDAP ID.

Foregoing corresponding relationship information may be configured toindicate the corresponding relationship of the SDAP entity, e.g., thecorresponding relationship between the SDAP entity and other entity, andmay also indicate the relationship among foregoing network slice ID, theDRB ID, the flow ID and the session ID. In addition, the foregoing upperlayer may be an entity located on an SDAP layer, e.g., a Non-accessstratum (NAS) entity.

In step 303, the upper layer transmits the data packet to thecorresponding SDAP entity, according to at least one of the networkslice ID, the SDAP ID, the flow ID, the session ID.

In the step, the corresponding SDAP ID may be determined, according tothe network slice ID of the data packet, the flow ID or session ID, andthen the data is transmitted to the corresponding SDAP entity.

In step 304, the SDAP entity adds the flow ID to the data packet, andtransmits the data packet with the flow ID to a PDCP entitycorresponding to DRB, according to a corresponding relationship betweenSDAP entity and DRB.

Optionally, the association relationship indication information includesany one of the following:

indicating that one SDAP entity corresponds to one flow;

indicating that one SDAP entity corresponds to one session unit (e.g.,PDU session);

indicating that one SDAP entity corresponds to one PDCP entity;

indicating that one SDAP entity corresponds to one Medium Access Control(MAC) entity;

indicating that one SDAP entity corresponds to one terminal.

In this implementation, one SDAP entity may be established for eachflow. For example, as shown in FIG. 4, a different flow is transmittedto a corresponding PDCP entity through a different SDAP.

It should be noted that, in the embodiment of the present disclosure,the corresponding relationship between flow and PDCP entity may bepre-configured. One PDCP entity may correspond to one, or more flows.And, one PDCP entity may correspond to one DRB, or one SDAP correspondsto one DRB.

In addition, in foregoing implementation, one SDAP entity may correspondto one PDU session. For example, as shown in FIG. 5, multiple flows ofone PDU session are respectively transmitted to a corresponding PDCPentity through one SDAP.

In addition, in foregoing implementation, one SDAP entity may correspondto one PDCP entity. For example, as shown in FIG. 6, flows correspondingto one PDCP entity are respectively transmitted to a corresponding PDCPentity through one SDAP.

In addition, in foregoing implementation, one SDAP entity may correspondto one MAC entity. For example, as shown in FIG. 6, flows of multiplePDU sessions corresponding to one MAC entity are respectivelytransmitted to a corresponding PDCP entity through the same SDAP entity,and then transmitted to a Radio Link Control (RLC) entity through PDCP,and finally transmitted to the MAC entity.

Besides, in foregoing implementation, one SDAP entity may correspond toone terminal. For example, as shown in FIG. 8, flows of multiple PDUsessions corresponding to multiple MAC entities of one terminal arerespectively transmitted to a corresponding PDCP entity through the sameSDAP entity, and then transmitted to an RLC entity through PDCP, andfinally transmitted to the MAC entity of the terminal.

Optionally, when the association relationship indication informationindicates that one SDAP entity corresponds to one MAC entity, theconfiguration information further includes an MAC ID.

In the implementation, when one SDAP entity corresponds to one MACentity, a corresponding MAC entity is indicated by using foregoing MACID.

Optionally, when the association relationship indication informationindicates that one SDAP entity corresponds to one PDU session, one SDAPentity corresponds to one PDCP entity, one SDAP entity corresponds toone MAC entity, or one SDAP entity corresponds to one terminal, thecorresponding relationship information further includes the associationrelationship indication information.

In the implementation, when the association relationship indicationinformation indicates that one SDAP entity corresponds to one PDUsession, one SDAP entity corresponds to one PDCP entity, one SDAP entitycorresponds to one MAC entity, or one SDAP entity corresponds to oneterminal, the association relationship indication information istransmitted to the upper layer through foregoing correspondingrelationship information. Subsequently, the upper layer determineswhether to provide auxiliary information of the data packet, accordingto the association relationship indication information, so as to enablethe SDAP to accurately transmit the data packet, and improve datatransmission performance.

For example, when the association relationship indication informationindicates that one SDAP entity corresponds to one PDU session, or oneSDAP entity corresponds to one PDCP entity, the method further includes:

the upper layer provides auxiliary information of the data packet, inwhich the auxiliary information includes flow ID.

Subsequently, when one SDAP entity corresponds to one PDU session, orone SDAP entity corresponds to one PDCP entity, the flow ID may beprovided, so as to enable the SDAP to accurately add the flow ID, andimprove data transmission performance.

In another example, when the association relationship indicationinformation indicates that one SDAP entity corresponds to one MACentity, or one SDAP entity corresponds to one terminal, the methodfurther includes:

the upper layer provides the auxiliary information of the data packet,in which the auxiliary information includes at least one of: a flow ID,a network slice ID, a session ID.

In the implementation, when one SDAP entity corresponds to one MACentity, or one SDAP entity corresponds to one terminal, the flow ID, thenetwork slice ID and session ID are provided, so as to enable the SDAPto accurately add the corresponding flow ID, perform an accuratetransmission according to the network slice ID and session ID, andimprove data transmission performance.

In the embodiment, the SDAP entity is established in advance accordingto configuration information which is configured by a network orpre-defined. The configuration information includes at least one of: anetwork slice ID, a DRB ID, a flow ID, a session ID, associationrelationship indication information. The SDAP entity indicatescorresponding relationship information of the SDAP entity to the upperlayer. The corresponding relationship information includes at least oneof: a network slice ID, a DRB ID, a flow ID, a session ID, an SDAP ID.The data packet is transmitted to the corresponding SDAP entity,according to a corresponding relationship among the network slice ID,the SDAP ID, the flow ID and session ID. The SDAP entity adds the flowID to the data packet, and transmits the data packet with the flow ID tothe PDCP entity corresponding to the DRB, according to the correspondingrelationship between SDAP entity and DRB. Subsequently, the SDAP entitymay be established flexibly, so as to improve the overall performance ofthe data transmitting end, and implement interactions among the upperlayer, SDAP entity and PDCP entity.

With reference to FIG. 9, FIG. 9 is a flowchart illustrating anotherdata transmission method, in accordance with an embodiment of thepresent disclosure. The method is applied to a data receiving end. Asshown in FIG. 9, the method includes the following steps.

In step 901, a PDCP entity receives a data packet from a datatransmitting end, and transmits the data packet to a corresponding SDAPentity, according to a flow ID carried by the data packet.

Foregoing corresponding SDAP entity may be an SDAP entity correspondingto above-mentioned flow ID.

In step 902, the SDAP entity forwards the data packet to an applicationprotocol layer, or, forwards the data packet to a corresponding networkslice, flow or PDU session.

In step 902, when the data receiving end is a user terminal, the SDAPentity forwards the data packet to the application protocol layer.However, when the data receiving end is a network device, the SDAPentity forwards the data packet to a corresponding network slice, flowand PDU session.

In the embodiment, the PDCP entity receives the data packet from thedata transmitting end, and transmits the data packet to thecorresponding SDAP entity, according to the flow ID carried by the datapacket. The SDAP entity forwards the data packet to the applicationprotocol layer, or, forwards the data packet to a corresponding networkslice, flow and PDU session, so as to implement interactions between theSDAP entity and the PDCP entity.

With reference to FIG. 10, FIG. 10 is a flowchart illustrating anotherdata transmission method, in accordance with an embodiment of thepresent disclosure. The method is applied to a data receiving end. Asshown in FIG. 10, the method includes the following steps.

In step 1001, an SDAP entity is established in advance according toconfiguration information which is configured by a network orpre-defined. The configuration information includes at least one of: anetwork slice ID, a DRB ID, a flow ID, a session ID, or associationrelationship indication information.

Foregoing process for establishing the SDAP entity may refer tocorresponding descriptions about the embodiment illustrated with FIG. 3,which is not repeated here. And the same beneficial effects may beachieved.

In step 1002, corresponding relationship information of the SDAP entityis indicated to an upper layer, through the SDAP entity, in which thecorresponding relationship information includes at least one of: anetwork slice ID, a DRB ID, a flow ID, a session ID, or an SDAP ID.

Foregoing corresponding relationship information of the SDAP entity mayrefer to corresponding descriptions about the embodiment illustratedwith FIG. 3, which is not repeated here. Besides, the same beneficialeffects may be achieved.

In step 1003, the PDCP entity receives the data packet from a datatransmitting end, and transmits the data packet to a corresponding SDAPentity, according to the flow ID carried by the data packet.

Foregoing corresponding SDAP entity may be an SDAP entity correspondingto above-mentioned flow ID.

In step 1004, the SDAP entity forwards the data packet to an applicationprotocol layer, or forwards the data packet to a corresponding networkslice, flow and PDU session.

Optionally, the process for the SDAP entity to forward the data packetto a corresponding network slice, flow and PDU session, includes:

the SDAP entity forwards the data packet to the corresponding networkslice, flow and PDU session, according to at least one of the networkslice ID, the SDAP ID, the flow ID, or the session ID.

In the implementation, the data packet may be accurately transmitted tothe corresponding network slice, flow and PDU session, according toforegoing corresponding relation, so as to improve data transmissionperformance.

Optionally, the association relationship indication information includesany one of the following:

indicating that one SDAP entity corresponds to one flow;

indicating that one SDAP entity corresponds to one PDU session;

indicating that one SDAP entity corresponds to one PDCP entity;

indicating that one SDAP entity corresponds to one MAC entity;

indicating that one SDAP entity corresponds to one terminal.

Foregoing association relationship indication information may refer tocorresponding descriptions about the embodiment illustrated with FIG. 3,which is not repeated here. And the same beneficial effects may beachieved.

Optionally, when the association relationship indication informationindicates that one SDAP entity corresponds to one MAC entity, theconfiguration information further includes an MAC ID.

Foregoing configuration information may refer to correspondingdescriptions about the embodiment illustrated with FIG. 3, which is notrepeated here. And the same beneficial effects may be achieved.

Optionally, when the association relationship indication informationindicates that one SDAP entity corresponds to one PDU session, indicatesthat one SDAP entity corresponds to one PDCP entity, indicates that oneSDAP entity corresponds to one MAC entity, or indicates that one SDAPentity corresponds to one terminal, the corresponding relationshipinformation further includes the association relationship indicationinformation.

Foregoing corresponding relationship information may refer tocorresponding descriptions about the embodiment illustrated with FIG. 3,which is not repeated here. And, the same beneficial effects may beachieved.

In the embodiment, the SDAP entity is established in advance, accordingto configuration information which is configured by a network orpre-defined, the configuration information includes at least one of: anetwork slice ID, a DRB ID, a flow ID, a session ID and associationrelationship indication information; corresponding relationshipinformation of the SDAP entity is indicated to the upper layer throughthe SDAP entity, in which the corresponding relationship informationincludes at least one of: a network slice ID, a DRB ID, a flow ID, asession ID, and an SDAP ID; the PDCP entity receives a data packet froma data transmitting end, and transmits the data packet to acorresponding SDAP entity, according to the flow ID carried by the datapacket. The SDAP entity forwards the data packet to an applicationprotocol layer, or, forwards the data packet to a corresponding networkslice, flow or PDU session. Subsequently, the SDAP entity may beestablished flexibly, so as to improve the overall performance of thedata transmitting end, and implement the interactions between the SDAPentity and PDCP entity.

With reference to FIG. 11, FIG. 11 is a flowchart illustrating a dataprocessing method. As shown in FIG. 11, the method includes thefollowing steps.

In step 1101, an SDAP entity is established in advance, according toconfiguration information which is configured by a network orprotocol-agreed, in which the configuration information includes atleast one of: a network slice ID, a DRB ID, a flow ID, a session ID, orassociation relationship indication information.

Foregoing network slice ID is configured to identify a network slice.And, a network slice may include multiple PDU sessions, while a PDUsession may include multiple flows. Foregoing DRB ID may be configuredto identify a DRB, and the DRB may correspond to the PDCP. Foregoingassociation relationship indication information is configured toindicate a corresponding relationship between above-mentioned SDAPentity and other entity. Subsequently, in step 201, after receivingforegoing configuration information, a corresponding SDAP entity may beestablished.

In step 1102, corresponding relationship information of the SDAP entityis indicated to an upper layer, by using the SDAP entity.

Foregoing corresponding relationship information may be configured toindicate a corresponding relationship of the SDAP entity, e.g., acorresponding relationship between the SDAP entity and other entity, andindicate a relationship among foregoing network slice ID, DRB ID, flowID and session ID. In addition, the foregoing upper layer may be anentity above the SDAP layer, e.g., a NAS layer entity.

In step 1103, data is transmitted among the upper layer, the SDAP entityand a PDCP entity, according to the corresponding relationshipinformation.

Foregoing data transmission among the upper layer, the SDAP entity andthe PDCP entity according to the corresponding relationship informationmay be implemented as follows. Transmitting data among foregoing upperlayer the SDAP entity and the PDCP entity, according to a correspondingrelationship among entities, or between entity and data, which isindicated by foregoing corresponding relationship information. And, suchtransmitting data may be sending data, or receiving data.

It should be noted that, the method may be applied to the data receivingend, or the data transmitting end in the system shown in FIG. 1.

In the embodiment, the SDAP entity is established in advance, accordingto configuration information which is configured by a network orprotocol-agreed. The configuration information includes at least one of:a network slice ID, a DRB ID, a flow ID, a session ID, or associationrelationship indication information. The corresponding relationshipinformation of the SDAP entity is indicated to the upper layer, by usingthe SDAP entity; and data is transmitted among the upper layer, the SDAPentity and the PDCP entity, according to the corresponding relationship,so as to implement the interactions among the upper layer, the SDAPentity and the PDCP entity.

With reference to FIG. 12, FIG. 12 is a flowchart illustrating anotherdata processing method, in accordance with an embodiment of the presentdisclosure. As shown in FIG. 12, the method includes the followingsteps.

In step 1201, an SDAP entity is established in advance, according toconfiguration information which is configured by a network orprotocol-agreed. The configuration information includes at least one of:a network slice ID, a DRB ID, a flow ID, a session ID, or associationrelationship indication information.

Optionally, the association relationship indication information includesany of the following:

indicating that one SDAP entity corresponds to one flow;

indicating that one SDAP entity corresponds to one PDU session;

indicating that one SDAP entity corresponds to one PDCP entity;

indicating that one SDAP entity corresponds to one MAC entity;

indicating that one SDAP entity corresponds to one terminal.

In the implementation, one SDAP entity may be established for each flow,e.g., as shown in FIG. 4, a different flow is transmitted to acorresponding PDCP entity through a different SDAP.

It should be noted that, in the embodiment of the present disclosure,the corresponding relationship between the flow and PDCP entity may bepre-configured, one PDCP entity may correspond to one or more flows, andone PDCP entity may correspond to one data bear, alternatively, one SDAPcorresponds to one DRB.

Besides, in foregoing implementation, one SDAP entity may correspond toone PDU session, e.g., as shown in FIG. 5, multiple flows of one PDUsession are transmitted to respective PDCP entity corresponding to eachflow, by using the same SDAP.

Besides, in foregoing implementation, one SDAP entity may correspond toone PDCP entity, e.g., as shown in FIG. 6, a flow corresponding to aPDCP entity is transmitted to the PDCP entity, by using the same SDAP.

Besides, in foregoing implementation, one SDAP entity may correspond toone MAC entity, e.g., as shown in FIG. 6, flows of multiple PDU sessionscorresponding to one MAC entity are respectively transmitted to a PDCPentity, which corresponds to each flow, by using the same SDAP entity,and then are transmitted to an RLC entity through the PDCP entity, andfinally to the MAC entity.

Besides, in foregoing implementation, one SDAP entity may correspond toone terminal, e.g., as shown in FIG. 8, flows of multiple PDU sessionscorresponding to multiple MAC entities of one terminal are respectivelytransmitted to a PDCP entity, which corresponds to each flow, by usingthe same SDAP entity, and then, is transmitted to an RLC entity throughthe PDCP entity, and finally to the MAC entity of the terminal.

In step 1202, corresponding relationship information of the SDAP entityis indicated to an upper layer through the SDAP.

Optionally, when the association relationship indication informationindicates that one SDAP entity corresponds to one MAC entity, theconfiguration information further includes an MAC ID.

In the implementation, when one SDAP entity corresponds to one MACentity, a corresponding MAC entity is indicated by using foregoing MACID.

Optionally, foregoing corresponding relationship information includes atleast one of: a network slice ID, a DRB ID, a flow ID, a session ID, oran SDAP ID.

A corresponding relationship among the network slice ID, the DRB ID, theflow ID, the session ID and the SDAP ID may be explicitly indicated, byusing foregoing network slice ID, DRB ID, flow ID, session ID and SDAPID. Subsequently, when the data is transmitted, the data may beaccurately transmitted through a corresponding entity, so as to improvethe performance of data transmission.

In step 1203, the upper layer determines a target SDAP entitycorresponding to to-be-transmitted target data packet, according to atleast one of the network slice ID, the SDAP ID, the flow ID or thesession ID.

When foregoing method is applied to the data transmitting end, e.g.,terminal or network device, the step 1203 may be performed.

Foregoing target data packet may be a data packet of a certain flow.Subsequently, a target SDAP entity corresponding to target data may bedetermined, by using above-mentioned corresponding relationship. Forexample, when one SDAP entity corresponds to one flow, a correspondingSDAP entity may be determined, by using flow of the target data packet.In another example, when one SDAP entity corresponds to one PDU session,a corresponding SDAP entity may be determined, by using a PDU sessioncorresponding to the target data packet. In still another example, whenone SDAP entity corresponds to one PDCP entity, a corresponding SDAPentity may be determined, by using a PDCP entity corresponding to a flowof the target data packet. In another example, when indicating that oneSDAP entity corresponds to one MAC entity, a corresponding SDAP entitymay be determined, by using a MAC entity corresponding to a PDU sessionof a flow, which corresponds to the target data packet. In anotherexample, when indicating that one SDAP entity corresponds to oneterminal, a corresponding SDAP entity may be determined, by using aterminal corresponding to the target data packet.

In step 1204, the upper layer transmits the target data packet to thetarget SDAP entity.

After determining the target SDAP entity, in step 304, the target datapacket may be transmitted to the target SDAP entity. Optionally, whenthe upper layer transmits the target data packet to the target SDAPentity, for the transmitted data packet, the upper layer may provide onepiece of, or multiple pieces of auxiliary information as follows:

a flow ID, a session ID, an SDAP ID, a DRB ID, a PDCP ID, or a MAC ID.

In step 1205, after adding a flow ID to the target data packet,according to a corresponding relationship between SDAP entity and DRB,the target SDAP entity forwards the target data packet to a target PDCPentity corresponding to the DRB.

Foregoing corresponding relationship between SDAP entity and DRB may bepreset. After adding the flow ID to the target data packet, acorresponding flow ID is added to the target data packet, besides, theflow ID of the target data packet may be added, according to networkconfiguration.

Besides, in the embodiment of the present disclosure, foregoing targetdata packet may be a TCP/IP data packet.

Optionally, when the association relationship indication informationindicates that one SDAP entity corresponds to one PDU session, or oneSDAP entity corresponds to one PDCP entity, the upper layer providesauxiliary information of the transmitted target data packet, in whichthe auxiliary information includes a flow ID.

In the implementation, a flow ID may be transmitted to the SDAP entity,so as to accurately enable the SDAP entity to add a corresponding flowID, and improve the performance of data transmission.

Optionally, when the association relationship indication informationindicates that one SDAP entity corresponds to one MAC entity, or oneSDAP entity corresponds to one terminal, the upper layer provides theauxiliary information of the transmitted target data packet, in whichthe auxiliary information includes at least one of: a flow ID, a networkslice ID, or a session ID.

In the implementation, a flow ID, a network slice ID and a session IDmay be transmitted to the SDAP entity, so as to accurately enable theSDAP entity to add a corresponding flow ID, implement an accuratetransmission according to the network slice ID and session ID, andimprove the performance of data transmission.

In the embodiment, after performing foregoing steps, data may beaccurately transmitted among the upper layer, the SDAP entity and thePDCP entity, so as to improve the transmitting performance of the datatransmitting end.

With reference to FIG. 13, FIG. 13 is a flowchart illustrating anotherdata processing data, in accordance with an embodiment of the presentdisclosure. As shown in FIG. 13, the method includes the followingsteps.

In step 1301, an SDAP entity is established in advance, according toconfiguration information which is configured by a network orprotocol-agreed, in which the configuration information includes atleast one of: a network slice ID, a DRB ID, a flow ID, a session ID, orassociation relationship indication information.

Optionally, the association relationship indication information includesany of the following:

indicating that one SDAP entity corresponds to one flow;

indicating that one SDAP entity corresponds to one PDU session;

indicating that one SDAP entity corresponds to one PDCP entity;

indicating that one SDAP entity corresponds to one MAC entity;

indicating that one SDAP entity corresponds to one terminal.

Regarding the association relationship indication information, it mayrefer to corresponding descriptions in the embodiment illustrated withFIG. 12, which is not repeated here.

In step 1302, corresponding relationship information of the SDAP entityis indicated to an upper layer, by using the SDAP entity.

Optionally, when the association relationship indication informationindicates that one SDAP entity corresponds to one MAC entity, theconfiguration information further includes a MAC ID.

In the implementation, when one SDAP entity corresponds to one MACentity, a corresponding MAC entity is indicated through foregoing MACID.

Optionally, foregoing corresponding relationship information includes atleast one of: a network slice ID, a DRB ID, a flow ID, a session ID, oran SDAP ID.

A corresponding relationship among the network slice ID, the DRB ID, theflow ID, the session ID and the SDAP ID may be explicitly indicated, byusing foregoing network slice ID, DRB ID, flow ID, session ID and SDAPID. Subsequently, when the data is transmitted, the data may betransmitted accurately through a corresponding entity, so as to improvethe performance of data transmission.

In step 1303, a PDCP entity receives a target data packet from atransmitting end.

When foregoing method is applied to a receiving end, e.g., a terminal ornetwork device, step 1303 may be performed.

Foregoing target data packet may be the target data packet in theembodiment illustrated with FIG. 12, which is not repeated here.Besides, the target data packet carries a flow ID.

In step 1304, the PDCP entity forwards the target data packet to acorresponding target SDAP entity, according to the flow ID carried bythe target data packet.

Foregoing corresponding target SDAP may be determined, by usingabove-mentioned association relationship indication information.

Optionally, when foregoing method is applied to a receiving end, and thereceiving end is a network device, after forwarding the target datapacket to the corresponding target SDAP entity, the method furtherincludes:

the target SDAP entity forwards the received target data packet to acorresponding network slice, flow and PDU session.

In the implementation, the target data packet may be transmitted to acorresponding network slice, flow and PDU session.

Optionally, when foregoing method is applied to a receiving end, and thereceiving end is a terminal, the target SDAP entity forwards thereceived data packet to an application protocol layer.

In the implementation, the terminal may forward the data packet to theapplication protocol layer through the SDAP entity.

In the embodiment, after performing foregoing steps, data may beaccurately received between the SDAP entity and the PDCP entity, so asto improve the receiving performance of the data receiving end.

With reference to FIG. 14, FIG. 14 is a schematic diagram illustratingstructure of a data transmitting end, in accordance with an embodimentof the present disclosure. As shown in FIG. 14, a data transmitting end1400 includes:

a first transmitting module 1401, configured to enable an upper layer totransmit a data packet to a corresponding SDAP entity, according to atleast one of a network slice ID, an SDAP ID, a flow ID, or a session ID;and,

a second transmitting module 1402, configured to enable the SDAP entityto add a flow ID to the data packet, and transmit the data packet withthe flow ID to a PDCP entity corresponding to a DRB, according to acorresponding relationship between the SDAP entity and the DRB.

Optionally, as shown in FIG. 15, the data transmitting end furtherincludes:

an establishing module 1403, configured to establish an SDAP entity inadvance, according to network configuration or pre-defined configurationinformation, in which the configuration information includes at leastone of: a network slice ID, a DRB ID, a flow ID, a session ID, orassociation relationship indication information; and,

an indicating module 1404, configured to indicate correspondingrelationship information of the SDAP entity to an upper layer, by usingthe SDAP entity, in which the corresponding relationship informationincludes at least one of: a network slice ID, a DRB ID, a flow ID, asession ID, or an SDAP ID.

Optionally, the association relationship indication information includesany of the following:

indicating that one SDAP entity corresponds to one flow;

indicating that one SDAP entity corresponds to one PDU session;

indicating that one SDAP entity corresponds to one PDCP entity;

indicating that one SDAP entity corresponds to one MAC entity;

indicating that one SDAP entity corresponds to one terminal.

Optionally, when the association relationship indication informationindicates that one SDAP entity corresponds to one MAC entity, theconfiguration information further includes a MAC ID.

Optionally, when the association relationship indication informationindicates that one SDAP entity corresponds to one PDU session, indicatesthat one SDAP entity corresponds to one PDCP entity, indicates that oneSDAP entity corresponds to one MAC entity, or indicates that one SDAPentity correspond to one terminal, the corresponding relationshipinformation further includes the association relationship indicationinformation.

Optionally, when the association relationship indication informationindicates that one SDAP entity corresponds to one PDU session, or oneSDAP entity corresponds to one PDCP entity, as shown in FIG. 16, thedata transmitting end 1400 further includes:

a first providing module 1405, configured to enable the upper layer toprovide auxiliary information of the data packet, in which the auxiliaryinformation includes the flow ID.

Optionally, when the association relationship indication informationindicates that one SDAP entity corresponds to one MAC entity, or oneSDAP entity corresponds to one terminal, as shown in FIG. 17, the datatransmitting end 1400 further includes:

a second providing module 1406, configured to enable the upper layer toprovide auxiliary information of the data packet, in which the auxiliaryinformation includes at least one of: a flow ID, a network slice ID, ora session ID.

It should be noted that, foregoing data transmitting end 1400 in theembodiment may be a data transmitting end in any implementation amongmethod embodiments of the present disclosure. In the method embodimentsof the present disclosure, any implementation of the data transmittingend may be achieved by foregoing data transmitting end 1400 in theembodiment, and the same beneficial effects may be achieved, which isnot repeated here.

With reference to FIG. 18, FIG. 18 is a schematic diagram illustratingstructure of a data receiving end, in accordance with an embodiment ofthe present disclosure, as shown in FIG. 18, a data receiving end 1800includes:

a receiving module 1801, configured to enable a PDCP entity to receive adata packet from a data transmitting end, and transmit the data packetto a corresponding SDAP entity, according to a flow ID carried by thedata packet;

a forwarding module 1802, configured to enable the SDAP entity toforward the data packet to an application protocol layer, or, forwardthe data packet to a corresponding network slice, flow, and PDU session.

Optionally, the forwarding module 1802 is specifically configured toenable the SDAP entity to forward the data packet to a correspondingnetwork slice, flow and PDU session, according to at least one of thenetwork slice ID, the SDAP ID, the flow ID or the session ID.

Optionally, as shown in FIG. 19, the data receiving end 1800 furtherincludes:

an establishing module 1803, configured to establish an SDAP entity inadvance, according to configuration information which is configured by anetwork or protocol-agreed, in which the configuration informationincludes at least one of: a network slice ID, a DRB ID, a flow ID, asession ID, or association relationship indication information;

an indicating module 1804, configured to indicate correspondingrelationship information of the SDAP entity to an upper layer, throughthe SDAP entity, in which the corresponding relationship informationincludes at least one of: a network slice ID, a DRB ID, a flow ID, asession ID, or an SDAP ID.

Optionally, the association relationship indication information includesat least one of:

indicating that one SDAP entity corresponds to one flow;

indicating that one SDAP entity corresponds to one PDU session;

indicating that one SDAP entity corresponds to one PDCP entity;

indicating that one SDAP entity corresponds to one MAC entity;

indicating that one SDAP entity corresponds to one terminal.

Optionally, when the association relationship indication informationindicates that one SDAP entity corresponds to one MAC entity, theconfiguration information further includes a MAC ID.

Optionally, when the association relationship indication informationindicates that one SDAP entity corresponds to one PDU session, indicatesthat one SDAP entity corresponds to one PDCP entity, indicates that oneSDAP entity corresponds to one MAC entity, indicates that one SDAPentity corresponds to one terminal, the corresponding relationshipinformation further includes the association relationship indicationinformation.

It should be noted that, in the embodiment, foregoing data receiving end1800 may be a data receiving end of any implementation in various methodembodiments of the present disclosure. Any implementation of the datareceiving end in various method embodiments of the present disclosuremay be achieved by foregoing data receiving end 1800 in the embodiment,and the same beneficial effects may be achieved, which is not repeatedhere.

With reference to FIG. 20, FIG. 20 is a schematic diagram illustratingstructure of a data processing device, in accordance with an embodimentof the present disclosure. As shown in FIG. 20, a data processing device2000 includes an establishing module 2001, an indicating module 2002,and a transmitting module 2003.

The establishing module 2001 is configured to establish an SDAP entityin advance, according to configuration information which is configuredby a network or protocol-agreed, in which the configuration informationincludes at least one of: a network slice ID, a DRB ID, a flow ID, asession ID, or association relationship indication information.

The indicating module 2002 is configured to indicate correspondingrelationship information of the SDAP entity to an upper layer throughthe SDAP entity.

The transmitting module 2003 is configured to transmit data among theupper layer, the SDAP entity and a PDCP entity, according to thecorresponding relationship.

Optionally, the association relationship indication information includesany of the following:

indicating that one SDAP entity corresponds to one flow;

indicating that one SDAP entity corresponds to one PDU session;

indicating that one SDAP entity corresponds to one PDCP entity;

indicating that one SDAP entity corresponds to one MAC entity;

indicating that one SDAP entity corresponds to one terminal.

Optionally, when the association relationship indication informationindicates that one SDAP entity corresponds to one MAC entity, theconfiguration information further includes a MAC ID.

Optionally, the corresponding relationship information includes at leastone of: a network slice ID, a DRB ID, a flow ID, a session ID, or anSDAP ID.

Optionally, when the data processing device 2000 is applied to atransmitting end, as shown in FIG. 21, the transmitting module 2003includes a first determining sub-module 20031, a transmitting sub-module20032, and a first forwarding sub-module 20033.

The first determining sub-module 20031 is configured to enable the upperlayer to determine a target SDAP entity corresponding to ato-be-transmitted target data packet, according to at least one of anetwork slice ID, an SDAP ID, a flow ID or a session ID.

The transmitting sub-module 20032 is configured to enable the upperlayer to transmit the target data packet to the target SDAP entity.

The first forwarding sub-module 20033 is configured to enable the targetSDAP entity to forward the target data packet to a target PDCP entitycorresponding to a DRB, after adding a flow ID to the target datapacket, according to a corresponding relationship between an SDAP entityand a DRB.

Optionally, when the association relationship indication informationindicates that one SDAP entity corresponds to one PDU session, or onePDCP entity, the upper layer provides auxiliary information of thetransmitted target data packet, in which the auxiliary informationincludes a flow ID.

Optionally, when the association relationship indication informationindicates that one SDAP entity corresponds to one MAC entity, or oneterminal, the upper layer provides the auxiliary information of thetransmitted target data packet, in which the auxiliary informationincludes at least one of: a flow ID, a network slice ID, or a sessionID.

Optionally, when the data processing device 2000 is applied to areceiving end, as shown in FIG. 22, the transmitting module 2003includes a receiving sub-module 20034 and a second forwarding module20035.

The receiving sub-module 20034 is configured to enable a PDCP entity toreceive a target data packet from a transmitting end.

The second forwarding module 20035 is configured to enable the PDCPentity to forward the target data packet to a corresponding SDAP entity,according to a flow ID carried by the target data packet.

Optionally, when the receiving end is a network device, as shown in FIG.23, the data processing device 2000 further includes:

a forwarding module 2004, configured to enable the target SDAP entity toforward the received target data packet to a corresponding networkslice, flow and PDU session.

Optionally, when the receiving end is a terminal, the target SDAP entityforwards the received data packet to an application protocol layer.

It should be noted that, in the embodiment, foregoing data processingdevice 2000 achieves any implementation of the data processing methods,which are provided by embodiments of the present disclosure. And, thesame beneficial effects may be achieved, which is not repeated here.

With reference to FIG. 24, FIG. 24 is a schematic diagram illustratingstructure of a data transmitting end, which is applied to an embodimentof the present disclosure. As shown in FIG. 24, a data transmitting end2400 includes: at least one processor 2401, a memory 2402, at least onenetwork interface 2404, and a user interface 2403. Each component withinthe data transmitting end 2400 may be coupled through a bus system 2405.It may be understood that, the bus system 2405 is configured toimplement connection communications among these components. In additionto data bus, the bus system 2405 further includes a power bus, a controlbus and a status signal bus. However, for clarity of description,various buses in FIG. 24 are labeled as the bus system 2405.

The user interface 2403 may include a display, a keyboard, or a clickdevice (e.g., a mouse, a track ball, a touch pad, or a touch screen, andso on).

It may be understood that, in the embodiment of the present disclosure,the memory 2402 may be a transitory memory, or a non-transitory memory,or may include both of a transitory memory and a non-transitory memory.The non-transitory memory may be a Read-Only Memory (ROM), aProgrammable ROM (PROM), an Erasable PROM (EPROM), an Electrically EPROM(EEPROM) or a flash memory. The transitory-memory may be a Random AccessMemory (RAM), which is taken as an external cache. By way ofillustration and not limitation, many forms of RAM are available, e.g.,a Static RAM (SRAM), a Dynamic RAM (DRAM), a Double Data Rate SDRAM(DDRSDRAM), an Enhanced SDRAM (ESDRAM), a Synchlink DRAM (SLDRAM) and aDirect Rambus RAM (DRRAM). The memory 2402 of the system and methoddescribed herein is intended to include, without limitation to, theseand any other suitable types of memory.

In some embodiments, the memory 2402 includes the following elements,executable modules, or data structures, or their subset, or theirextension set: an Operating System (OS) 24021 and an application 24022.

The OS 24021 includes various system programs, such as, a frame layer, acore library layer, a driver layer, and so on, which are configured toimplement various basic services and process hardware-based tasks. Theapplication 24022 includes various applications, e.g., a Media Player, aBrowser, and so on, which are configured to implement variousapplication services. The program implementing the method in theembodiment of the present disclosure may be included by the application24022.

In the embodiment of the present disclosure, by calling the program orinstruction stored in the memory 2402, specifically, the program orinstruction stored by the application 2402, the processor 2401 isconfigured to:

enable an upper layer to transmit a data packet to a corresponding SDAPentity, according to at least one of a network slice ID, an SDAP ID, aflow ID, or a session ID.

The SDAP entity adds the flow ID to the data packet, and transmits thedata packet with the flow ID to a PDCP entity corresponding to a DRB,according to a corresponding relationship between an SDAP entity and aDRB.

Foregoing method provided by the embodiment of the present disclosuremay be applied to the processor 2401, or may be implemented by theprocessor 2401. The processor 2401 may be an integrated circuit chipwith signal processing capability. In the implementation process,various steps of foregoing method may be completed, by using theintegrated logic circuit of hardware in the processor 2401, or by usinginstructions in the form of software. Foregoing processor 2401 may be ageneral processor, a Digital Signal Processor (DSP), an ApplicationSpecific Integrated Circuit (ASIC), a Field Programmable Gate Array(FPGA), or other programmable logic devices, discrete gates ortransistor logic devices, discrete hardware components. Each method,block and logical block diagram in the embodiments of the presentdisclosure may be implemented, or executed. The general processor may bea micro-processor, or any conventional processor, and so on. Combiningwith method steps in the embodiments of the present disclosure, it maybe directly implemented by a hardware decoding processor, or may beexecuted by a combination of hardware and software modules in thedecoding processor. Software modules may be located in a mature storagemedium in the field, such as, an RAM, a flash memory, an ROM, a PROM, anelectrically erasable programmable memory, a register. The storagemedium is located in the memory 2402, the processor 2401 readsinformation in the memory 2402, and completes foregoing method steps incombination with the hardware.

It may be understood that, these embodiments described in the presentdisclosure may be implemented by hardware, software, firmware,middleware, microcode, or a combination thereof. For hardwareimplementation, a processing unit may be implemented in one or moreASICs, DSPs, DSP Devices (DSPDs), Programmable Logic Device (PLDs),FPGAs, general processors, controllers, micro-controllers,micro-processors, other electronic units or combinations thereof forperforming the functions described in the present disclosure.

For software implementation, the techniques described in the presentdisclosure may be implemented by modules (e.g., procedures, functions,etc.) that perform the functions of the present disclosure. Softwarecodes may be stored in the memory, and executed by the processor. Thememory may be implemented in the processor or external to the processor.

Optionally, before the upper layer transmits the data packet to thecorresponding SDAP entity, according to at least one of the networkslice ID, the SDAP ID, the flow ID, or the session ID, the processor2401 is further configured to:

establish an SDAP entity in advance, according to configurationinformation which is configured by a network or protocol-agreed, inwhich the configuration information includes at least one of: a networkslice ID, a DRB ID, a flow ID, a session ID, or association relationshipindication information; and,

indicate corresponding relationship information of the SDAP entity tothe upper layer through the SDAP entity, in which the correspondingrelationship information includes at least one of: a network slice ID, aDRB ID, a flow ID, a session ID, or an SDAP ID.

Optionally, the association relationship indication information includesany of the following:

indicating that one SDAP entity corresponds to one flow;

indicating that one SDAP entity corresponds to one PDU session;

indicating that one SDAP entity corresponds to one PDCP entity;

indicating that one SDAP entity corresponds to one MAC entity;

indicating that one SDAP entity corresponds to one terminal.

Optionally, when the association relationship indication informationindicates that one SDAP entity corresponds to one MAC entity, theconfiguration information further includes a MAC ID.

Optionally, when the association relationship indication informationindicates that one SDAP entity corresponds to one PDU session, indicatesthat one SDAP entity corresponds to one PDCP entity, indicates that oneSDAP entity corresponds to one MAC entity, or indicates that one SDAPentity corresponds to one terminal, the corresponding relationshipinformation further includes the association relationship indicationinformation.

Optionally, when the association relationship indication informationindicates that one SDAP entity corresponds to one PDU session, orindicates that one SDAP entity corresponds to one PDCP entity, theprocessor 2401 is further configured to:

enable the upper layer to provide auxiliary information of the datapacket, in which the auxiliary information includes the flow ID.

Optionally, when the association relationship indication informationindicates that one SDAP entity corresponds to one MAC entity, orindicates that one SDAP entity corresponds to one terminal, theprocessor 2401 is further configured to:

enable the upper layer to provide the auxiliary information of the datapacket, in which the auxiliary information includes at least one of: aflow ID, a network slice ID, or a session ID.

It should be noted that, in the embodiment, forgoing data transmittingend 2400 achieves any implementation of the data transmission method,which is provided by an embodiment of the present disclosure. And, thesame beneficial effects may be achieved, which is not repeated here.

With reference to FIG. 25, FIG. 25 is a schematic diagram illustratingstructure of a data receiving end, which is applied to an embodiment ofthe present disclosure. As shown in FIG. 25, a data receiving end 2500includes: at least one processor 2501, a memory 2502, at least onenetwork interface 2504, and a user interface 2503. Each component in thedata receiving end 2500 is coupled through a bus system 2505. It may beunderstood that, the bus system 2505 is configured to implementconnection communications among these components. In addition to databus, the bus system 2505 further includes a power bus, a control bus,and a status signal bus. However, for clarity of description, in FIG.25, various buses are labeled as the bus system 2505.

The user interface 2503 may include a display, a keyboard or a clickdevice (e.g., a mouse, a track ball, a touch pad, or a touch screen, andso on).

It may be understood that, in the embodiment of the present disclosure,the memory 2502 may be a transitory memory, or a non-transitory memory,or may include both of a transitory memory and a non-transitory memory.The non-transitory memory may be an ROM, a PROM, an EPROM, an EEPROM, ora flash memory. The transitory memory may be an RAM, which is taken asan external cache. By way of illustration and not limitation, many formsof RAM are available, e.g., an SRAM, a DRAM, an SDRAM, a DDRSDRAM, anESDRAM, an SLDRAM and a DRRAM. The memory 2502 of systems and methodsdescribed in the present disclosure is intended to include, withoutlimitation to, these and any other suitable types of memory.

In some embodiments, the memory 2502 stores the following elements,executable modules or data structures, or their subsets, or theirextension sets: an OS 25021 and an application 25022.

The OS 25021 includes various system programs, e.g., a frame layer, acore library layer, a driver layer, etc., which are configured toimplement various basic services and hardware-based tasks. Theapplication 25022 includes various applications, e.g., a Media Player, aBrowser, and so on, which are configured to implement variousapplication services. The program implementing the method in theembodiment of the present disclosure may be included in the application25022.

In the embodiment of the present disclosure, by calling the program orinstruction stored by the memory 2502, specifically, the program orinstruction stored in the application 25022, the processor 2501 isconfigured to:

enable a PDCP entity to receive a data packet from a data transmittingend, and transmit the data packet to a corresponding SDAP entity,according to a flow ID carried by the data packet; and,

the SDAP entity forward the data packet to an application protocollayer, or forward the data packet to a corresponding network slice, aflow, and a PDU session.

Foregoing method provided by the embodiment of the present disclosuremay be applied to the processor 2501, or may be implemented by theprocessor 2501. The processor 2501 may be an integrated circuit chipwith signal processing capability. In the implementation process,various steps of foregoing method may be completed by the integratedlogical circuit of hardware in the processor 2501, or by instructions inthe form of software. Foregoing processor 2501 may be a generalprocessor, a DSP, an ASIC, a FPGA or other programmable logic devices,discrete gates or transistor logic devices, discrete hardwarecomponents. Each method, block and logic block diagram provided by theembodiments of the present disclosure may be implemented or executed.The general processor may be a micro-processor, or any conventionalprocessor, and so on. Combining with method steps provided byembodiments of the present disclosure, it may be directly implemented asa hardware decoding processor, or may be executed by a combination ofhardware and software modules in the decoding processor. Softwaremodules may be located in a mature storage medium in the field, such as,an RAM, a flash memory, an ROM, a PROM, an electrically erasableprogrammable memory, a register. The storage medium is located in thememory 2502, the processor 2501 reads information from the memory 2502,and completes foregoing method steps in combination with the hardware.

It may be understood that, these embodiments described in the presentdisclosure may be implemented by hardware, software, firmware,middleware, microcode, or a combination thereof. For hardwareimplementation, a processing unit may be implemented in one or moreASICs, DSPs, DSP Devices (DSPDs), Programmable Logic Device (PLDs),FPGAs, general processors, controllers, micro-controllers,micro-processors, other electronic units or combinations thereof forperforming the functions described in the present disclosure.

For software implementation, the techniques described in the presentdisclosure may be implemented by modules (e.g., procedures, functions,etc.) that perform the functions of the present disclosure. Softwarecodes may be stored in the memory, and executed by the processor. Thememory may be implemented in the processor or external to the processor.

Optionally, the process of the SDAP entity forwarding the data packet tothe corresponding network slice, flow and PDU session, which is executedby the processor 2501, includes:

the SDAP entity forwards the data packet to the corresponding networkslice, flow and PDU session, according to at least one of a networkslice ID, an SDAP ID, a flow ID, or a session ID.

Optionally, the processor 2501 is further configured to:

establish an SDAP entity in advance, according to configurationinformation which is configured by a network or protocol-agreed, inwhich the configuration information includes at least one of: a networkslice ID, a DRB ID, a flow ID, a session ID, or association relationshipindication information; and,

indicate corresponding relationship information of the SDAP entity to anupper layer through the SDAP entity, in which the correspondingrelationship information includes at least one of: a network slice ID, aDRB ID, a flow ID, a session ID, or an SDAP ID.

Optionally, the association relationship indication information includesany of the following:

indicating that one SDAP entity corresponds to one flow;

indicating that one SDAP entity corresponds to one PDU session;

indicating that one SDAP entity corresponds to one PDCP entity;

indicating that one SDAP entity corresponds to one MAC entity;

indicating that one SDAP entity corresponds to one terminal.

Optionally, when the association relationship indication informationindicates that one SDAP entity corresponds to one MAC entity, theconfiguration information further includes a MAC ID.

Optionally, when the association relationship indication informationindicates that one SDAP entity corresponds to one PDU session, indicatesthat one SDAP entity corresponds to one PDCP entity, indicates that oneSDAP entity corresponds to one MAC entity, or indicates that one SDAPentity corresponds to one terminal, the corresponding relationshipinformation further includes the association relationship indicationinformation.

It should be noted that, in the embodiment, foregoing data receiving end2500 achieves any implementation of the data transmission method, whichis provided by the embodiment of the present disclosure. And, the samebeneficial effects may be achieved, which is not repeated here.

With reference to FIG. 26, FIG. 26 is a schematic diagram illustratingstructure of a data processing device, which is applied to an embodimentof the present disclosure. As shown in FIG. 26, a data processing device2600 includes: at least one processor 2601, a memory 2602, at least onenetwork interface 2604 and a user interface 2603. Each component in thedata processing device 2600 is coupled through a bus system 2605. It maybe understood that, the bus system 2605 is configured to implementconnection communications among these components. In addition to databus, the bus system 2605 further includes a power bus, a control bus anda status signal bus. However, for clarity of description, in FIG. 26,various buses are labeled as the bus system 2605.

The user interface 2603 may include a display, a keyboard, or a clickdevice (e.g., a mouse, a track ball, a touch pad, or a touch screen).

It may be understood that, in the embodiment of the present disclosure,the memory 2602 may be a transitory memory, or a non-transitory memory,or may include both of a transitory memory and a non-transitory memory.The non-transitory memory may be an ROM, a PROM, an EPROM, an EEPROM, ora flash memory. The transitory memory may be an RAM, which is taken asan external cache. By way of illustration and without limitation, manyforms of RAM are available, e.g., an SRAM, a DRAM, an SDRAM, a DDRSDRAM,an ESDRAM, an SLDRAM and a DRRAM. The memory 2602 of systems and methodsdescribed in the present disclosure is intended to include, withoutlimitation to, these and any other suitable types of memory.

In some embodiments, the memory 2602 stores the following elements,executable modules, or data structures, or their subsets, or theirextension sets: an OS 26021 and an application 26022.

The OS 26021 includes various system programs, e.g., a frame layer, acore library layer, a driver layer, and so on, which are configured toimplement various basic services, and process hardware-based tasks. Theapplication 26022 includes various applications, e.g., a Media Player, aBrowser, and so on, which are configured to implement variousapplication services. The program implementing the method in theembodiment of the present disclosure may be included by the application26022.

In the embodiment of the present disclosure, by calling the program orinstruction stored in the memory 2602, specifically, the program orinstruction stored in the application 26022, the processor 2601 isconfigured to:

establish an SDAP entity in advance, according to configurationinformation which is configured by a network or protocol-agreed, inwhich the configuration information includes at least one of: a networkslice ID, a DRB ID, a flow ID, a session ID, or association relationshipindication information;

indicate corresponding relationship information of the SDAP entity to anupper layer through the SDAP entity; and,

transmit data among the upper layer, the SDAP entity, and a PDCP entityaccording to the corresponding relationship information.

Foregoing method provided by the embodiment of the present disclosuremay be applied to the processor 2601, or may be implemented by theprocessor 2601. The processor 2601 may be an integrated circuit chipwith signal processing capability. In the implementation process, eachstep of foregoing method may be completed, by using the integrated logiccircuit of hardware in the processor 2601, or by using instructions inthe form of software. Foregoing processor 2601 may be a generalprocessor, a DSP, an ASIC, an FPGA, or other programmable logic device,discrete gate or transistor logic device, discrete hardware components.Each method, block and logic block diagram provided by embodiments ofthe present disclosure may be implemented or executed. The generalprocessor may be a micro-processor, or any conventional processor, andso on. Combining with method steps provided by embodiments of thepresent disclosure, it may be directly implemented as a hardwaredecoding processor, or may be executed by a combination of hardware andsoftware modules in the decoding processor. Software modules may belocated in a mature storage medium in the field, such as, an RAM, aflash memory, an ROM, a PROM, an electrically erasable programmablememory, a register. The storage medium is located in the memory 2602,the processor 2601 reads information from the memory 2602, and completesforegoing method steps in combination with the hardware.

It may be understood that, these embodiments described in the presentdisclosure may be implemented by hardware, software, firmware,middleware, microcode, or a combination thereof. For hardwareimplementation, a processing unit may be implemented in one or moreASICs, DSPs, DSP Devices (DSPDs), Programmable Logic Device (PLDs),FPGAs, general processors, controllers, micro-controllers,micro-processors, other electronic units or combinations thereof forperforming the functions described in the present disclosure.

For software implementation, the techniques described in the presentdisclosure may be implemented by modules (e.g., procedures, functions,etc.) that perform the functions of the present disclosure. Softwarecodes may be stored in the memory, and executed by the processor. Thememory may be implemented in the processor or external to the processor.

Optionally, the association relationship indication information includesat least one of:

indicating that one SDAP entity corresponds to one flow;

indicating that one SDAP entity corresponds to one PDU session;

indicating that one SDAP entity corresponds to one PDCP entity;

indicating that one SDAP entity corresponds to one MAC entity;

indicating that one SDAP entity corresponds to one terminal.

Optionally, when the association relationship indication informationindicates that one SDAP entity corresponds to one MAC entity, theconfiguration information further includes a MAC ID.

Optionally, the corresponding relationship information includes at leastone of: a network slice ID, a DRB ID, a flow ID, a session ID, or anSDAP ID.

Optionally, when the data processing method is applied to a transmittingend, the step of transmitting data among the upper layer, the SDAPentity and the PDCP entity, according to the corresponding relationshipinformation, which is performed by the processor 2601, includes:

determining a target SDAP entity corresponding to a to-be-transmittedtarget data packet, according to at least one of a network slice ID, anSDAP ID, a flow ID, or a session ID;

the upper layer transmits the target data packet to the target SDAPentity;

after adding the flow ID to the target data packet, the target SDAPentity forwards the target data packet with the flow ID to a target PDCPentity corresponding to a DRB, according to a corresponding relationshipbetween an SDAP entity and a DRB.

Optionally, when the association relationship indication informationindicates that one SDAP entity corresponds to one PDU session, orindicates that one SDAP entity corresponds to one PDCP entity, the upperlayer provides auxiliary information of the transmitted target datapacket, in which the auxiliary information includes a flow ID.

Optionally, when the association relationship indication informationindicates that one SDAP entity corresponds to one MAC entity, orindicates that one SDAP entity corresponds to one terminal, the upperlayer provides the auxiliary information of the transmitted target datapacket, in which the auxiliary information includes at least one of: aflow ID, a network slice ID, or a session ID.

Optionally, when the data processing method is applied to a receivingend, the step of transmitting data among the upper layer, the SDAPentity and the PDCP entity, according to the corresponding relationshipinformation, which is performed by the processor 2601, includes:

the PDCP entity receives the target data packet from a transmitting end;

the PDCP entity forwards the target data packet to the correspondingtarget SDAP entity, according to the flow ID carried by the target datapacket.

Optionally, when the receiving end is a network device, after the stepof forwarding the target data packet to the corresponding SDAP entity,the processor 2601 is further configured to:

enable the target SDAP entity to forward the received target data packetto a corresponding network slice, flow and PDU session.

Optionally, when the receiving end is a terminal, the target SDAP entityforwards the received data packet to an application protocol layer.

It should be noted that, in the embodiment, foregoing data processingdevice 2600 achieves any implementation of the data processing method,which is provided by the embodiment of the present disclosure. And, thesame beneficial effects may be achieved, which is not repeated here.

In an eighth aspect, an embodiment of the present disclosure alsoprovides a computer readable storage medium, which stores a datatransmission program. When the data transmission program is executed bythe processor, steps of data transmission method at the datatransmitting end provided by embodiments of the present disclosure isimplemented.

In a ninth aspect, an embodiment of the present disclosure also providesa computer readable storage medium, which stores a data transmissionprogram. When the data transmission program is executed by theprocessor, steps of data transmission method at the data receiving endprovided by embodiments of the present disclosure is implemented.

Persons having ordinary skill in the art may learn that, units andalgorithm steps of each example described by embodiments of the presentdisclosure may be implemented in electronic hardware, or in acombination of computer software and electronic hardware. Whether thesefunctions are performed by hardware or software depends on specificapplication and design constraints of technical solutions. For eachspecific application, a person skilled in the art may adopt a differentmethod to implement the described functions. However, suchimplementation should not be considered to go beyond the scope of thepresent disclosure.

Persons having ordinary skill in the art may clearly learn that, forconvenience and conciseness of description, the specific working processof above-described system, device and unit may refer to correspondingprocess of foregoing method embodiments, which is not repeated here.

In the embodiments of the present disclosure, it should be understoodthat, the disclosed devices and methods may be implemented with othermethods. For example, the above-described device embodiments are onlyillustrative, e.g., the division of the unit is only a logic functiondivision. In practical implementation, there may be another divisionmethod. For example, multiple units or components may be combined, orintegrated into another system, or some features may be omitted, or notexecuted. From another point, the mutual coupling or direct coupling, orcommunication connection shown or discussed may be indirect coupling, orcommunication connections through some interfaces, devices, or units,which may be electronic, mechanical, or in other form.

Units described as separate components may be, or may be not physicallyseparate. A component displayed as a unit may be, or may be not aphysical unit, that is, it may be located in one place, or may bedistributed to multiple network units. According to practicalrequirements, some units or all the units may be selected to implementthe objective of solutions in the embodiments of the present disclosure.

In addition, in each embodiment of the present disclosure, variousfunctional units may be integrated into a processing unit.Alternatively, each unit physically exists alone. Still alternatively,two or more units may be integrated into one unit.

When the functions are implemented in the form of software functionalunit, which is sold or used as an independent product, such softwarefunctional unit may be stored in a computer readable storage medium.According to such understandings, the technical solution of the presentdisclosure, or, a part contributing to the prior art, or a part of thetechnical solution may be embodied in the form of a software product.The computer software produce is stored in one storage medium, includingseveral instructions to enable a computer device (may be a PersonalComputer (PC), a server, or a network device, etc.) to implement all thesteps, or some steps in the method of each embodiment of the presentdisclosure. Foregoing storage medium includes various media that canstore program codes, such as a U disk, a mobile hard disk, an ROM, anRAM, a disk, or a Compact Disk (CD), and so on.

Foregoing is only specific implementations of the present disclosure.However, protection scope of the present disclosure is not limited. Anychanges or substitutions that are obvious to those skilled in the artwithin the scope of the present disclosure are covered by the scope ofthe present disclosure. Therefore, the protection scope of thedisclosure should be determined by the scope of the claims.

What is claimed is:
 1. A data transmission method, applied to a datatransmitting end, comprising: transmitting, by an upper layer, a datapacket to a corresponding Service Data Adaptation Protocol (SDAP)entity, according to at least one of a network slice identifier, an SDAPidentifier, a flow identifier or a session identifier; adding, by theSDAP entity, a flow identifier corresponding to the data packet, to thedata packet; and, transmitting the data packet with the flow identifierto a Packet Data Convergence Protocol (PDCP) entity corresponding to aData Radio Bearer (DRB), according to a corresponding relationshipbetween the SDAP entity and the DRB; wherein before transmitting, by theupper layer, the data packet to the corresponding SDAP entity, accordingto at least one of the network slice identifier, the flow identifier orthe session identifier, the method further comprises: establishing theSDAP entity in advance, according to configuration information which isconfigured by a network or pre-defined: wherein the configurationinformation comprises at least one of the network slice identifier, aDRB identifier, the flow identifier, the session identifier, orassociation relationship indication information; wherein the associationrelationship indication information comprises any one of: indicatingthat one SDAP entity corresponds to one flow; indicating that one SDAPentity corresponds to one Protocol Data Unit (PDU) session; indicatingthat one SDAP entity corresponds to one PDCP entity; indicating that oneSDAP entity corresponds to one Medium Access Control (MAC) entity; and,indicating that one SDAP entity corresponds to one terminal.
 2. Themethod according to claim 1, wherein indicating correspondingrelationship information of the SDAP entity to the upper layer throughthe SDAP entity; wherein the corresponding relationship informationcomprises at least one of the network slice identifier, the DRBidentifier, the flow identifier, the session identifier or the SDAPidentifier.
 3. The method according to claim 1, wherein when theassociation relationship indication information indicates that one SDAPentity corresponds to one MAC entity, the configuration informationfurther comprises MAC ID.
 4. The method according to claim 1, whereinwhen the association relationship indication information indicates thatone SDAP entity corresponds to one PDU session, indicates that one SDAPentity corresponds to one PDCP entity, indicates that one SDAP entitycorresponds to one MAC entity, or indicates that one SDAP entitycorresponds to one terminal, the corresponding relationship informationfurther comprises the association relationship indication information.5. The method according to claim 4, wherein when the associationrelationship indication information indicates that one SDAP entitycorresponds to one PDU session, or indicates that one SDAP entitycorresponds to one PDCP entity, the method further comprises: providing,by the upper layer, auxiliary information of the data packet, whereinthe auxiliary information comprises the flow identifier.
 6. The methodaccording to claim 4, wherein when the association relationshipindication information indicates that one SDAP entity corresponds to oneMAC entity, or indicates that one SDAP entity corresponds to oneterminal, the method further comprises: providing, by the upper layer,auxiliary information of the data packet, wherein the auxiliaryinformation comprises at least one of the flow identifier, the networkslice identifier, or the session identifier.
 7. A data transmissionmethod, applied to a data receiving end, comprising: receiving, by aPacket Data Convergence Protocol (PDCP) entity, a data packet from adata transmitting end, and transmitting the data packet to acorresponding Service Data Adaptation Protocol (SDAP) entity accordingto a flow identifier carried by the data packet; and, forwarding, by theSDAP entity, the data packet to an application protocol layer, orforwarding the data packet to a corresponding network slice, a flow anda Protocol Data Unit (PDU) session; wherein the method furthercomprises: establishing the SDAP entity in advance, according toconfiguration information which is configured by a network orprotocol-agreed; wherein the configuration information comprises atleast one of a network slice identifier, a Data Radio Bearer (DRB)identifier, the flow identifier, a session identifier, or associationrelationship indication information; wherein the associationrelationship indication information comprises any one of: indicatingthat one SDAP entity corresponds to one flow; indicating that one SDAPentity corresponds to one PDU session; indicating that one SDAP entitycorresponds to one PDCP entity; indicating that one SDAP entitycorresponds to one Medium Access Control (MAC) entity; indicating thatone SDAP entity corresponds to one terminal.
 8. The method according toclaim 7, wherein forwarding by the SDAP entity the data packet to thecorresponding network slice, flow and PDU session, comprises:forwarding, by the SDAP entity, the data packet to the correspondingnetwork slice, flow and PDU session, according to at least one of anetwork slice identifier, an SDAP identifier, the flow identifier, or asession identifier.
 9. The method according to claim 7, furthercomprising: indicating corresponding relationship information of theSDAP entity to an upper layer through the SDAP entity; wherein thecorresponding relationship information comprises at least one of thenetwork slice identifier, the DRB identifier, the flow identifier, thesession identifier or an SDAP identifier.
 10. The method according toclaim 7, wherein when the association relationship indicationinformation indicates that one SDAP entity corresponds to one MACentity, the configuration information further comprises an MAC ID. 11.The method according to claim 7, wherein when the associationrelationship indication information indicates that one SDAP entitycorresponds to one PDU session, indicates that one SDAP entitycorresponds to one PDCP entity, indicates that one SDAP entitycorresponds to one MAC entity, or indicates that one SDAP entitycorresponds to one terminal, the corresponding relationship informationfurther comprises the association relationship indication information.12. A data transmitting end, comprising: a processor, a memory, anetwork interface and a user interface, wherein the processor, thememory, the network interface and the user interface are coupled througha bus system, the processor is configured to read a program from thememory to perform steps of: transmitting, by an upper layer, a datapacket to a corresponding Service Data Adaptation Protocol (SDAP)entity, according to at least one of a network slice identifier, an SDAPidentifier, a flow identifier or a session identifier; adding, by theSDAP entity, a flow identifier corresponding to the data packet, to thedata packet; and, transmitting the data packet with the flow identifierto a Packet Data Convergence Protocol (PDCP) entity corresponding to aData Radio Bearer (DRB), according to a corresponding relationshipbetween the SDAP entity and the DRB; wherein the processor is furtherconfigured to read the program from the memory to perform steps of:establishing the SDAP entity in advance, according to configurationinformation which is configured by a network or pre-defined; wherein theconfiguration information comprises at least one of the network sliceidentifier, a DRB identifier, the flow identifier, the sessionidentifier, or association relationship indication information; whereinthe association relationship indication information comprises any oneof: indicating that one SDAP entity corresponds to one flow; indicatingthat one SDAP entity corresponds to one Protocol Data Unit (PDU)session; indicating that one SDAP entity corresponds to one PDCP entity;indicating that one SDAP entity corresponds to one Medium Access Control(MAC) entity; and, indicating that one SDAP entity corresponds to oneterminal.
 13. The data transmitting end according to claim 12, whereinthe processor is further configured to read the program from the memoryto perform steps of: indicating corresponding relationship informationof the SDAP entity to the upper layer through the SDAP entity; whereinthe corresponding relationship information comprises at least one of thenetwork slice identifier, the DRB identifier, the flow identifier, thesession identifier or the SDAP identifier.
 14. The data transmitting endaccording to claim 12, wherein when the association relationshipindication information indicates that one SDAP entity corresponds to oneMAC entity, the configuration information further comprises MAC ID; or,when the association relationship indication information indicates thatone SDAP entity corresponds to one PDU session, indicates that one SDAPentity corresponds to one PDCP entity, indicates that one SDAP entitycorresponds to one MAC entity, or indicates that one SDAP entitycorresponds to one terminal, the corresponding relationship informationfurther comprises the association relationship indication information.15. The data transmitting end according to claim 14, wherein when theassociation relationship indication information indicates that one SDAPentity corresponds to one PDU session, or indicates that one SDAP entitycorresponds to one PDCP entity, the processor is further configured toread the program from the memory to perform steps of: providing, by theupper layer, auxiliary information of the data packet, wherein theauxiliary information comprises the flow identifier.
 16. The datatransmitting end according to claim 14, wherein when the associationrelationship indication information indicates that one SDAP entitycorresponds to one MAC entity, or indicates that one SDAP entitycorresponds to one terminal, the processor is further configured to readthe program from the memory to perform steps of: providing, by the upperlayer, auxiliary information of the data packet, wherein the auxiliaryinformation comprises at least one of the flow identifier, the networkslice identifier, or the session identifier.